Dynamic reader-instigated categorization and distribution restriction of mailing list threads

ABSTRACT

A method of regulating electronic message traffic is proposed. The method comprises sending an electronic message as part of a thread, receiving a response to the message, and tabulating said response in a counter. A data processing system compares the counter to a threshold and, in response to the comparing step, designates the thread as off-topic.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 11/011,250, filed on Dec. 14, 2004 now U.S. Pat. No. 7,548,953,entitled “Method and System for Dynamic Reader-Instigated Categorizationand Distribution Restriction on Mailing List Threads”. Applicants claimbenefit of priority under 35 U.S.C. §120 to U.S. patent application Ser.No. 11/011,250, which is incorporated by reference herein in itsentirety and for all purposes.

BACKGROUND OF THE INVENTION

1. Technical Field

The present invention relates in general to data processing and inparticular to improving utility of threaded email lists. Still moreparticularly, the present invention relates to a system, method andcomputer program product for regulating message traffic on threadedemail lists.

2. Description of the Related Art

The advent of electronic mail has enabled a host of new methods ofinexpensive communication. When discussing the advantages of e-mail,most users envision e-mail in its most basic form, which is thecommunication of text messages from an individual user to anotherindividual user. This ability to deliver text messages hasrevolutionized interpersonal communications, both for business and forpersonal data content.

The availability of ubiquitous, low-cost, electronic messaging hasenabled a host of spin-off applications. While the simple mail transferprotocol (SMTP) has enabled users to communicate with each otherindividually, additional mass-communication functionalities have arisenfrom related applications such as listserv. Listserv, and other similarproducts, operate on the principal of allowing an individual user tosend to a pre-defined list of other users. The overall concept oflistserv is that an individual user sends a message once to a server.Upon receipt of the individual user's message, the server then resendsthe message to a pre-defined list of users.

Most listserv user lists are dedicated to interest-specific topics. Forexample, a listserv will be dedicated to a specific neighborhood groupor alumni of a specific college. The predefined list of a listservcommunity, which often have well-defined common interest allow anindividual user to direct a message to a group of like-minded users costeffectively and with great speed. The sending user is therefore insuredof a reasonable expectation that the receiving users will have interestin messages related to the topic of the listserv.

This sense of community of common interest which makes the listserv souseful, is also the basis of a great weakness of listserv technology.The weakness arises from listserv's common strength, the common interestand sense of community among the users. Over time, many listservsdegenerate into off-topic discussion as users identify the tangentialcommon interests of the user list, which are not related to the subjectof the list.

This devolution of the listserv content creates a choking traffic inmessages, and, while dedicated to some of the common interests of somemembers of the list, threatens the utility of the list by diluting theon-topic content of the list with a tremendous amount of off-topiccontent that is only marginally or tangentially related to the list. Astime progresses, the ability of the listserv to transmit usefulinformation dedicated to its intended topic is diminished as regularsubscribers develop a frustration with the off-topic posts. What isneeded is a way for list subscribers to efficiently identify off-topicthreads and to seamlessly filter future posts made on those threads.

SUMMARY OF THE INVENTION

A method of regulating electronic message traffic is proposed. Themethod comprises sending an electronic message as part of a thread,receiving a response to the message, and tabulating said response in acounter. A data processing system compares the counter to a thresholdand, in response to the comparing step, designates the thread asoff-topic.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features believed characteristic of the invention are setforth in the appended claims. The invention itself, however, as well asa preferred mode of use, further objects and advantages thereof, willbest be understood by reference to the following detailed descriptionsof an illustrative embodiment when read in conjunction with theaccompanying drawings, wherein:

FIG. 1 depicts a block diagram of a network environment including dataprocessing systems equipped with computer program products forregulating message traffic in accordance with a preferred embodiment ofthe present invention;

FIG. 2A illustrates a block diagram of a listserv content message datastructure with substructures for regulating message traffic inaccordance with a preferred embodiment of the present invention;

FIG. 2B depicts a block diagram of a listserv notice message datastructure with substructures for regulating message traffic inaccordance with a preferred embodiment of the present invention;

FIG. 3 is a high level logical flowchart of a method for filtering,packaging, and sending messages to regulate message traffic inaccordance with a preferred embodiment of the present invention; and

FIG. 4 is a high level logical flowchart of a method for tabulatingresults and sending notices to regulate message traffic in accordancewith a preferred embodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

The present invention provides a method, system and computer programproduct for regulating message traffic by employing mailing list serversoftware equipped with the capability to tabulate votes receivedrelative to messages within specific threads sent to the mailing list.Filtering is driven by subscribers to the mailing list sending voteswith respect to an off-topic thread to a vote tabulator through emailclients, which can be extended to perform this operation. Once athreshold number of votes against a particular thread has been reached,the mailing list server could notify subscribers that a thread has beenlisted as off-topic and that a further request for the thread will berequired to continue access to the thread.

The present invention has several advantages over existing filteringsolutions. First, it distributes the duty of identification of theoff-topic thread among subscribers. Second, it centralizes processing ofoff-topic thread tabulation so that each subscriber is not required tocreate his own filtering mechanism. Third, the present inventionconserves bandwidth and processing power by stopping off-topic trafficat a mail server. Fourth, the present invention also provides a dynamicfiltering system that does not clutter e-mail clients with shortduration filtering rules.

With reference now to the figures and in particular with reference toFIG. 1, a block diagram of the network environment including dataprocessing systems equipped with computer program products forregulating message traffic in accordance with a preferred embodiment ofthe present invention is depicted. The network environment depicted inFIG. 1 includes network 100 for transmitting messages between firstclient 102, server 104, second client 106 and third client 108. Each offirst client 102, second client 106 and third client 108 contains ane-mail client, such as e-mail client 110 in third client 108. E-mailclient 110 contains a send tool 112 and a receive tool 114. Receive tool114 is used for receiving messages from server 104, send tool 112 isused for sending messages to server 104.

Server 104 contains an operating system 116, applications 118 and serversoftware 120. In the present invention, server software 120 contains areceive tool 122, a tabulate tool 124, a package tool 126 and abroadcast tool 128. Receive tool 122 receives messages from first client102, second client 106 and third client 108 and also handles the messagereceiving functions of the present invention. Packaging tool 126prepares messages for delivery to first client 102, second client 106and third client 108 by broadcast tool 128.

The present invention involves the sending of several messages, asdepicted in FIG. 1. First among these, first client 102 sends firstlistserv candidate message 130 to receive tool 122 on server 104.Receive tool 122 sends a first content distribution message 132 topackage tool 126. Package tool 126 sends a first packaged message 134 tobroadcast tool 128. Broadcast tool 128 then sends a first listservbroadcast 136 to each of first client 102, second client 106 and thirdclient 108. At third client 108, receive tool 114 on e-mail client 110receives first broadcast message 136. In response to first broadcastmessage 136, send tool 112 on e-mail client 110 of third client 108sends protest message 138 to receive tool 122. Receive tool 122 sends atabulate message 140 to tabulate tool 124. A protest message, such asprotest message 138, will typically be sent in response to a particularmessage on a thread.

Tabulate tool 124 is further capable of sending an off-topicnotification 142 to package tool 126. Whenever an off-topic notification142 is received by package tool 126, package tool 126 sends a de-listingnotification 144 to broadcast tool 128. Broadcast tool 128 then sends aremoval notice 146 to receive tool 114 on e-mail client 110 of thirdclient 108. Removal notice 146 is also sent by broadcast tool 128 tofirst client 102 and second client 106. In response to removal notice146, second client 106 can choose to send a resubscribe message 156 toreceive tool 122 on server software 120 of server 104. Receive tool 122sends a resubscribe notice 158 to package tool 126.

Subsequently, when first client 102 sends second listserv candidatemessage 148 to receive tool 122 on server software 120 of server 104,receive tool 146 sends second content distribution message 150 topackage tool 126. Package tool 126 sends restricted broadcast message152 to broadcast tool 128. Broadcast tool 128 sends second listservbroadcast 154 to first client 102 and second client 106, but not tothird client 108.

Further, the present invention uses and server software 120 maintainsseveral data structures. Server software 120 maintains off-topic threadlist 160, which contains a list of all threads that have tabulate toolhas determined to be off-topic. Server software 120 also maintainsrecipient list 164, containing addresses of all recipients of a givenlistserv and removed list 166, containing addresses of all recipients ofa given listserv who have opted to resubscribe to a particular thread.Finally, server software 120 maintains a vote table 162, containing atable correlating the number of protests received on each of severalthreads and a list of email addresses of protesting clients. All toolslisted above may be implemented as part of a single software program oras independent processes. Additionally, in alternative environments,some processing functions listed as occurring on server 120 may beexecuted on individual clients.

Turning now to FIG. 2A, a block diagram of a listserv content messagedata structure with substructures for regulating message traffic inaccordance with a preferred embodiment of the present invention isdepicted. Listserv content message data structure 200 is represented inFIG. 1 as first listserv broadcast 136 and second listserv broadcast154. Listserv content message data structure 200 contains a header 202,a protest tool 204, a re-subscribe tool 206, content 208 and,optionally, one or more attachments 210.

Header 202 contains routing information for transmission of message 200across network 100 by broadcast tool 128. On most mailing lists, threadshave a unique thread identifier in the email headers. An example ofcontent from header 202, many of the components of which are well knownto those skilled in the art, could contain information as listed below:

--- Date: Tue, 30 Nov 2004 16:05:38 -0700 From: Firstname Lastname<userid@domain.topleveldomain> Subject: RE: [listserv name] veryinteresting mail Sender:listname-list-bounces@listserver.domain.topleveldomain To: List Name <listname-list@ listserver.domain.topleveldomain > Errors-to:listname-list-bounces@ listserver.domain.topleveldomain Reply-to: ListName < listname-list@ listserver.domain.topleveldomain > Message-id:<8C7BA7940746324BA6DFF77AAC3A4D607798@ userid@domain.topleveldomain >MIME-version: 1.0 X-MIMEOLE: Produced By Program V6.5.6944.0Content-type: text/plain; charset=us-ascii Content-transfer-encoding:quoted-printable Precedence: list Thread-Topic: [listserv name] veryinteresting email thread-index: AcTXDucZQRqZYu6rTTqJ7eJyGAvVggAIg8hAContent-class: urn:content-classes:message X-BeenThere: listname-list@listserver.domain.topleveldomain X-Mailman-Version: 2.1.4 List-Post: <listname-list@ listserver.domain.topleveldomain > List-Subscribe:<http://url.listname.domain.topleveldomain/cgi-bin/mailman/listinfo/listname-list>, <mailto:listname-list-request@domain.topleveldomain?subject= subscribe> List-Unsubscribe:<http://url.listname.domain.topleveldomain/cgi-bin/mailman/listinfo/listname-list>,  <mailto:listname-list-request@domain.topleveldomain?subject=  unsubscribe >List-Archive: <http:// url.listname.domain.topleveldomain/pipermail/listname-list> List-Help:<mailto:listname-list-request@domain.topleveldomain?subject= help>List-Id: List name <listname-list@domain.topleveldomain > ---

A preferred embodiment will make particular use of the “Thread-Topic”and “thread-index” lines:

--- Thread-Topic: [listserv name] very interesting email thread-index:AcTXDucZQRqZYu6rTTqJ7eJyGAvVggAIg8hA ---

In a preferred embodiment, the “Thread-Topic” and “thread-index” linesare used as unique identifiers for threads; messages can be associatedwith threads through these identifiers in the headers. The off-topicmarker can simply take the form of an email header. Three variations fora preferred embodiment are:

--- Thread-Topic: [listname] very interesting email thread-index:AcTXDucZQRqZYu6rTTqJ7eJyGAvVggAIg8hA Off-Topic: No --- Thread-Topic:[listname] very interesting email thread-index:AcTXDucZQRqZYu6rTTqJ7eJyGAvVggAIg8hA Off-Topic: Yes, branch_votes=7 ---Thread-Topic: [listname] very interesting email thread-index:AcTXDucZQRqZYu6rTTqJ7eJyGAvVggAIg8hA Off-Topic: Suspect ---

In the variations given above, branch_votes is the number of off-topicvotes given against all of the messages under a given thread root. Insome alternative embodiments, email client 110 can categorize themessage based on the Off-Topic header. Of course, list subscribers can,as detailed below, request that server software 120 not withholdmessages that earn the “Off-Topic: Yes” header.

Protest tool 204 contains instructions, executable by send tool 112 ofemail client 110, for sending protest message 138 to receive tool 122 onserver 104. Re-subscribe tool 206 contains instructions, executable bysend tool 112 of email client 110, to send an automatic re-subscribemessage. An automatic resubscribe message is equivalent to resubscribemessage 156, but is capable of being sent prior to receiving removalnotice 146. When a resubscribe message 156 is received, server software120 will add the address of the sending client to removed list 166.Content 208 contains textual and/or graphical message content, such asthat received in first listserv candidate message 130. Attachments 210may comprise one or more textual, graphical, and or data files, whichmay be received in first listserv candidate message 130.

With reference now to FIG. 2B, a block diagram of listserv removalnotice message data structure with substructures for regulating messagetraffic in accordance with a preferred embodiment of the presentinvention is depicted. Removal notice 146 contains removal statement212, complaint tool 214, thread digest 216 and re-subscribe tool 218.Removal statement 212 contains data (e.g. an auto-generated textmessage) informing the user that a thread has been declared off-topicand removed, and contains textual instructions for using complaint tool214, thread digest 216 and re-subscribe tool 218. Complaint tool 214contains instructions for send tool 112 to protest listing of aparticular listing is off-topic. Thread digest 216 contains a digest ofall messages listed on the current thread. Re-subscribe tool 218contains instructions, executable by send tool 112 of email client 110,to send a re-subscribe message 156.

Turning now to FIG. 3, a high-level logical flowchart of a method forfiltering, packaging and sending messages to regulate message traffic inaccordance with a preferred embodiment of the present invention isdepicted. The process depicted in FIG. 3 embodies a series of decisionsand actions that will facilitate the processing of a message receivedfrom a client for transmission to other clients through server software120. The process starts at step 300. The process then moves to step 302,which depicts receive tool 122 on server software 120 of server 104,receiving a message for broadcast transmission, such as first listservcandidate message 130 or second listserv candidate message 148. Theprocess next moves to step 304. At step 304, receive tool 122 on serversoftware 120 of server 104 determines whether the message received instep 302 is directed to a designated off-topic thread by comparing thetopic of the message received in step 302 to off-topic thread list 160.

Off-topic thread list 160 will contain a listing of threads, whichthreads can contain both on-topic and off-topic messages. Off-topicmessages tend to start at the root of one branch, while other branchesmay contain on-topic messages. Some embodiments of the present inventionmay utilize off-topic branch roots be the basis for future replies tomessages under that root. An example of off-topic thread list 160 isgiven below, where Y=off-topic, N=on-topic, S=suspect.

3035 Oct 14 Jonathon Zapter (31) N [uug] dvd project 3036 Oct 14 DanilDephouru (70) N |-> 3037 Oct 14 Spencer Smitt (57) N |-> 3038 Oct 15Larry Rusnucci (14) N | |-> 3039 Oct 15 Hanry Wadslo (41) N | | |-> 3040Oct 15 James Hatfeeld (21) N | |-> 3041 Oct 15 Larry Rasnucci (20) N |->3042 Oct 15 Yodel Tokna (48) N | |-> 3043 Oct 15 Brianne Warck (15) N ||-> 3044 Oct 15 Jamisen Quint (95) N |->In the example above, if message 3037 is voted off-topic, then atabulate tool 124 will label messages 3038, 3039, and 3040 automaticallyas off-topic, and the entire thread rooted at message 3035 is calledinto suspicion. The updated status of off-topic thread list 160 is givenbelow:

3035 Oct 14 Jonathon Zapter (31) S [uug] dvd project 3036 Oct 14 DanilDephouru (70) S |-> 3037 Oct 14 Spencer Smitt (57) Y |-> 3038 Oct 15Larry Rusnucci (14) Y | |-> 3039 Oct 15 Henry Wadslo (41) Y | | |-> 3040Oct 15 James Hatfeeld (21) Y | |-> 3041 Oct 15 Larry Rusnucci (20) S |->3042 Oct 15 Yodel Tokna (48) S | |-> 3043 Oct 15 Brianne Warck (15) S ||-> 3044 Oct 15 Jamisen Quint (95) S |->If message 3041 is voted on-topic, then 3042 and 3043 are automaticallycategorized as on-topic. Message 3044 is continued to be flagged assuspect, and individual recipients can decide how they wish to treatsuspect messages when received. The updated status of off-topic threadlist 160 is given below:

3035 Oct 14 Jonathon Zapter (31) S [uug] dvd project 3036 Oct 14 DanilDephouru (70) S |-> 3037 Oct 14 Spencer Smitt (57) Y |-> 3038 Oct 15Larry Rusnucci (14) Y | |-> 3039 Oct 15 Henry Wadslo (41) Y | | |-> 3040Oct 15 James Hatfeeld (21) Y | |-> 3041 Oct 15 Larry Rusnucci (20) N |->3042 Oct 15 Yodel Tokna (48) N | |-> 3043 Oct 15 Brianne Warck (15) N ||-> 3044 Oct 15 Jamisen Quint (95) S |->

In an alternative embodiment, as votes come in, the status of themessages in the thread can change. Mail clients can be configured tostay up-to-date by requesting status updates from the mailing listserver. If clients cannot do so, then they can at least know when theyhave received messages that are sent under a flagged root (e.g. 3037)and take appropriate action.

If receive tool 122 on server software 120 of server 104 determines thatthe message received at step 302 is not directed to a designatedoff-topic thread, then the process next moves to step 306. At step 306,server software 120 adds protest tool 204 and re-subscribe tool 206 tothe message received in step 302. This addition is accomplished inseveral steps. First, receive tool 122 sends first content distributionmessage 132 to package tool 126 for packaging. Package tool 126 thencreates listserv content message data structure 200 by combining content208 and attachments 210 received in first content distribution message132 with header 202, protest tool 204 and re-subscribe tool 206. Theprocess then moves to step 308, which depicts package tool 126 on serversoftware 120 of server 104 listing all available recipients to receivethe message received in step 302. This listing of recipients isaccomplished by inserting into header 202 a list of all availablerecipients who are members of the appropriate listserv.

The process next proceeds to step 310. At step 310, server software 120on server 104 sends the message received for transmission in step 302.The sending step is accomplished in multiple steps. First, package tool126 sends first package message 134 containing listserv content messagedata structure 200 to broadcast tool 128. Broadcast tool 128 thentransmits first listserv broadcast 136 across network 100 to each memberof the listserv (e.g., first client 102, second client 106 and thirdclient 108). The process then ends at step 312.

Returning to step 304, if receive tool 122 on server software 120 toserver 104 determines that the message received at step 302 is anoff-topic message, then the process next moves to step 314, whichdepicts server software 120 adding protest tool 204 to the messagereceived in step 302. This addition is accomplished in several steps.First, receive tool 122 sends second content distribution message 150 topackage tool 126 for packaging. Next, package tool 126 creates listservcontent message data structure 200 by combining content 208 andattachments 210 received in first content distribution message 132 withheader 202 and protest tool 204.

The process then proceeds to step 316, which depicts server software 120listing the remaining recipients. This listing of recipients isaccomplished by inserting into header 202 a list of all remainingrecipients who are members of the appropriate listserv and have sent aresubscribe message 156 (as listed in removed table 162) with referenceto a the thread containing the message. The process then moves to step310, which is described above.

With reference now to FIG. 4, a high-level logical flowchart of a methodfor tabulating results and sending notices to regulate message trafficin accordance with a preferred embodiment of the present invention isdepicted. The process depicted in FIG. 4 embodies a series of decisionsand actions that will facilitate the processing of protest messagesreceived from a client by server software 120 and the designation ofthreads as being off-topic. The process starts at step 400. The processthen moves to step 402, which depicts receive tool 122 of serversoftware 120 on server 104 receiving a protest in the form of protestmessage 138 from send tool 112 on third client 108. Protest message 138from send tool 112 on third client 108 will have been generated by auser, dissatisfied with the content of a thread, by executing theinstructions contained in protest tool 204 in listserv content messagedata structure 200 The process then moves to step 404.

At step 404, server software 120 determines if the protest received instep 402 applies to a thread already designated as off-topic. Thisdetermination is accomplished by sending a tabulate message 140containing all of the content of protest message 138 to tabulate tool124. Tabulate tool 124 then examines the content of tabulate message 140and compares the thread designated in tabulate message 140 to off-topicthread list 160, which contains an internal list of designated off-topicthreads. If, in step 404, server software 120 determines that protestmessage 138 applies to a designated off-topic thread, then the processends at step 406. If, at step 404, server software 120 determines thatthe protest message 138 does not apply to a designated off-topic thread,then the process moves to step 408.

At step 408, protest message 138 is tabulated by recording and countingprotest message 138. The process then moves to step 410 at whichtabulate tool 124 determines whether the number of protest messages P,stored in vote table 162 is greater than a configurable threshold T. IfP is not greater than T, then the process ends at step 406. If P isgreater than T, then the process moves to step 412, which depictstabulate tool 124 designating the thread referenced by protest message138 as being an off-topic thread. The value of T can be user-configureddepending on the tolerance of listserv users for off-topic threads. In apreferred embodiment, T will typically be configured to represent aselected percentage the subscriber base of a given listserv. In otherembodiments, T may represent an absolute number of users. The processthen moves to step 414, which depicts server software 120 sending aremoval notice 146 to first client 102, second client 106 and thirdclient 108. The sending of a removal notice 146 is accomplished bytabulate tool 124 sending an off-topic notification 142 to package tool126. Package tool 126 then sends a de-listing notification 144 tobroadcast tool 128. Broadcast tool 128 then sends a removal notice 146to first client 102, second client 106, and third client 108 and addsthe thread to off-topic thread list 160.

As it has been disclosed herein, the present invention requiresresubscription of a user after a thread is designated as being offtopic. Alternative embodiments of the present invention may furtherallow a user to unsubscribe from a thread by protesting against thethread, without regard to whether other users have designated the threadoff-topic. Further, as it has been disclosed herein, the presentinvention applies to listserv software, but one skilled in the art willquickly realize that the present invention applies equally to allthreaded reflector or threaded forwarding-based messaging software.

The advent of electronic mail has enabled a host of new methods ofinexpensive communication. When discussing the advantages of e-mail,most users envision e-mail in its most basic form, which is thecommunication of text messages from an individual user to anotherindividual user. This ability to deliver text messages hasrevolutionized interpersonal communications, both for business and forpersonal data content. The present invention relates to a system, methodand computer program product for regulating message traffic on threadedemail lists.

The present invention has several advantages over existing filteringsolutions. First, it distributes the duty of identification of theoff-topic thread among subscribers. Second, it centralizes processing ofoff-topic thread tabulation so that each subscriber is not required tocreate his own filtering mechanism. Third, the present inventionconserves bandwidth and processing power by stopping off-topic trafficat a mail server. Fourth, the present invention also provides a dynamicfiltering system that does not clutter e-mail clients with shortduration filtering rules.

While the invention has been particularly shown as described withreference to a preferred embodiment, it will be understood by thoseskilled in the art that various changes in form and detail may be madetherein without departing from the spirit and scope of the invention. Itis also important to note that although the present invention has beendescribed in the context of a fully functional computer system, thoseskilled in the art will appreciate that the mechanisms of the presentinvention are capable of being distributed as a program product in avariety of forms, and that the present invention applies equallyregardless of the particular type of signal bearing media utilized toactually carry out the distribution. Examples of signal bearing mediainclude, without limitation, recordable type media such as floppy disksor CD ROMs and transmission type media such as analog or digitalcommunication links.

1. A method of regulating message traffic, said method comprising:sending a first message as part of a thread, said first messageincluding a toolset including multiple tools that are each executable bya client receiving the first message to regulate message traffic; inresponse to receiving at least one response to said first message,designating said thread as off-topic; in response to receipt of a secondmessage for transmission, determining if said second message is directedto the thread designated as off-topic, and if so, packaging the secondmessage with a more limited toolset than the first message, wherein themore limited tool set includes at least one tool executable by a clientreceiving the second message to regulate message traffic; andthereafter, sending the second message.
 2. The method of claim 1,further comprising sending notice to one or more thread recipients thatsaid thread is off-topic.
 3. The method of claim 1, wherein said sendingsaid second message comprises sending the second message to a morelimited subset of one or more previous thread recipients.
 4. The methodof claim 1, wherein said sending said second message comprises sendingsaid second message to a complete set of one or more previous threadrecipients.
 5. The method of claim 1, wherein said more limited tool setcomprises a voting tool.
 6. The method of claim 1, wherein said morelimited tool set comprises a re-subscribe tool.
 7. The method of claim2, wherein sending said notice further comprises including are-subscribe tool in said notice.
 8. A system for regulating messagetraffic, said system comprising: means for sending a first message aspart of a thread, said first message including a toolset includingmultiple tools that are each executable by a client receiving the firstmessage to regulate message traffic; means, responsive to receiving atleast one response to said first message, designating said thread asoff-topic; means, responsive to receipt of a second message fortransmission, for determining if said second message is directed to thethread designated as off-topic, and if so, for packaging the secondmessage with a more limited toolset than the first message, wherein themore limited toolset includes at least one tool executable by a clientreceiving the second message to regulate message traffic; and means forthereafter sending the second message.
 9. The system of claim 8, furthercomprising means for sending notice to one or more thread recipientsthat said thread is off-topic.
 10. A computer program productcomprising: a non-transitory computer-readable storage medium; programcode stored within the non-transitory computer-readable storage mediumthat when executed by a computer cause the computer to perform: sendinga message as part of a thread, said first message including a toolsetincluding multiple toes that are each executable by a client receivingthe first message to regulate message traffic; in response to receivingat least one response to said first message designating said thread asoff-topic; in response to receipt of a second message for transmission,determining if said second message is directed to the thread designatedas off-topic, and if so, packaging the second message with a morelimited toolset than the first message, wherein the more limited toolset includes at least one tool executable by a client receiving thesecond message to regulate message traffic; and thereafter, sending thesecond message.
 11. The computer program product of claim 10, whereinthe program code further causes the computer to send notice to one ormore thread recipients that said thread is off-topic.
 12. The system ofclaim 8, wherein means said sending said second message comprises meansfor sending the second message to a more limited subset of one or moreprevious thread recipients.
 13. The system of claim 8, wherein said morelimited tool set comprises a voting tool.
 14. The system of claim 8,wherein said more limited tool set comprises a re-subscribe tool. 15.The system of claim 9, wherein said notice includes a re-subscribe tool.16. The computer program product of claim 10, wherein said sending saidsecond message comprises sending the second message to a more limitedsubset of one or more previous thread recipients.
 17. The computerprogram product of claim 10, wherein said more limited tool setcomprises a voting tool.
 18. The computer program product of claim 10,wherein said more limited tool set comprises a re-subscribe tool. 19.The computer program product of claim 11, wherein said notice includes are-subscribe tool.